Quantum: add az quantum workspace user list command - #10215
Draft
Konstantin Averkiev (kaverkiev) wants to merge 4 commits into
Draft
Quantum: add az quantum workspace user list command#10215Konstantin Averkiev (kaverkiev) wants to merge 4 commits into
az quantum workspace user list command#10215Konstantin Averkiev (kaverkiev) wants to merge 4 commits into
Conversation
|
Hi Konstantin Averkiev (@kaverkiev), |
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
microsoft-github-policy-service
Bot
requested review from
Ethan Yang (necusjz),
ZelinWang (wangzelin007) and
Yong Zhang (yonzhan)
August 13, 2026 19:11
microsoft-github-policy-service
Bot
added
Quantum
Member
|
/azp run |
|
Azure Pipelines: Successfully started running 2 pipeline(s). |
Konstantin Averkiev (kaverkiev)
changed the title
az quantum workspace user list command
|
|
||
| info = WorkspaceInfo(cmd, resource_group_name, workspace_name) | ||
| scope = _get_workspace_resource_id(info) | ||
| return list_role_assignments(cmd, assignee=assignee, assignee_object_id=assignee_object_id, role=role, scope=scope, include_inherited=include_inherited) |
Contributor
There was a problem hiding this comment.
should we use only QUANTUM_WORKSPACE_DATA_CONTRIBUTOR_ROLE_ID for role here? I think we should not allow to pass role as an argument unless we have a good reason
Member
|
/azp run |
|
Azure Pipelines: Successfully started running 2 pipeline(s). |
Member
|
/azp run |
|
Azure Pipelines: Successfully started running 2 pipeline(s). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 PR Validation —⚠️ Review suggested
Summary
Adds az quantum workspace user list to complete the az quantum workspace user command group. Lists the users, groups, and service principals with access to an Azure Quantum workspace.
Details
Lists Azure RBAC role assignments scoped to the workspace.
Supports --assignee, --assignee-object-id, and --role filters (reuses the existing workspace user params).
Adds an opt-in --include-inherited flag to also surface access inherited from the parent resource group and subscription (assignments granted above the workspace scope).
Testing
New unit tests: scope construction, --include-inherited pass-through, and table transformer.
Added a live user list check to the test_workspace_user scenario.
Manually verified against a live workspace (default vs --include-inherited).
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
General Guidelines
azdev style <YOUR_EXT>locally? (pip install azdevrequired)python scripts/ci/test_index.py -qlocally? (pip install azdevrequired)For new extensions:
About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update
src/index.jsonautomatically.You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify
src/index.json.